Mobile Phone As A One-Way Recorded Transmitter Over A Cellular Network

ABSTRACT

Agencies oftentimes desire to monitor personnel in the field during the course of their duties. To provide flexible monitoring capabilities to agencies, a common mobile device such as a mobile phone is converted for use as a radio-based listening system to collect and transmit audio data. Phone features and accessories are leveraged to collect additional data for transmission. Collected data is streamed or otherwise transmitted to monitoring devices at the agency or in the field for operational oversight and recordation.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/491,823, filed May 31, 2011, and U.S. Provisional Application No.61/549,657, filed Oct. 20, 2011, which are incorporated by referenceherein in their entirety.

BACKGROUND

1. Field of Art

The present disclosure generally relates to the field of undercoveroperations and more specifically to using a mobile phone as anundercover device.

2. Background of the Invention

Police officers and other agents “operators” oftentimes conductinvestigations in the field during the course of their duties. In manycases, these investigations require direct support and oversight at anadministrative level. For example, an operator conducting an undercoversting in a high-risk situation may have a support team monitoring theoperator directly in the field and interfacing with administration at anagency. Traditionally, the operator would use a radio-based covertlistening system that can be hidden (e.g., under a shirt) or otherwiseembedded (e.g., in or on an electronic device or object) to conceal itsnature and protect operators' cover. The listening device would thentransmit audio data back to the support team, which would relay databack to the agency.

However, with widespread publicity of listening devices in movies andthe like, the physical nature of a given device can lead to itsdiscovery or detection, which poses additional risks for the operatorsthemselves. Additionally, traditional bugs have other inherentdeficiencies when used in the field, such as requiring line-of-sight orphysical proximity to a base station and the support team. Although somenewer bug systems seek to provide sufficient concealability among otherdesirable features, they are oftentimes prohibitively expensive and yet,still fail to mitigate the above deficiencies. Furthermore, such systemsare not rapidly deployable as they typically require support personnelother than immediate backup.

SUMMARY

The above and other issues are addressed by a method and computer systemfor configuring a telephonic device as a one-way recorded transmitter(mobile bug). An embodiment of the method comprises receivinginformation in response to a connection request from a telephonic deviceto a virtual number. The information received includes a transmittingnumber corresponding to the telephonic device and the virtual number.The telephonic device is identified as the mobile bug in response tomatching the transmitting number of the telephonic device with atransmitting number stored in association with the virtual number in amapping table. With the mobile bug identified, the method furtherincludes transmitting instructions for connecting the mobile bug to thevirtual number to permit monitoring of the mobile bug. Outgoing audio tothe mobile bug is disabled.

An embodiment of the system comprises a server having a one or moreprocessors and a non-transitory computer-readable storage medium storingcomputer program code. When executed, the computer program code causesthe server to receive information in response to a connection requestfrom a telephonic device to a virtual number. The information receivedincludes a transmitting number corresponding to the telephonic deviceand the virtual number. The server identifies the telephonic device asthe mobile bug in response to matching the transmitting number of thetelephonic device with a transmitting number stored in association withthe virtual number in a mapping table. With the mobile bug identified,the server transmits instructions for connecting the mobile bug to thevirtual number with outgoing audio to the mobile bug disabled to permitmonitoring of the mobile bug.

BRIEF DESCRIPTION OF THE DRAWINGS

The teachings of the embodiments can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings.

FIG. 1A is a block diagram illustrating an environment for implementinga system for using a mobile phone as a one-way recorded transmitter“mobile bug” according to one example embodiment.

FIG. 1B is a block diagram illustrating an operating environment of amobile bug according to one example embodiment.

FIG. 2 is a block diagram illustrating a bug module according to oneexample embodiment.

FIG. 3A is an interaction diagram illustrating a method for provisioningand mapping virtual numbers for operating and monitoring a mobile bugaccording to one example embodiment.

FIG. 3B and 3C are tables illustrating example embodiments of virtualnumber mapping for operating and monitoring a mobile bug.

FIG. 4 is an interaction diagram illustrating a method for connecting amonitoring device or mobile bug to a virtual number according to oneexample embodiment.

FIG. 5 is an interaction diagram illustrating a method for operating amobile bug according to one example embodiment.

FIG. 6 is an interaction diagram illustrating a method for monitoring amobile bug according to one example embodiment.

DETAILED DESCRIPTION

The Figures (FIG.) and the following description relate to preferredembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesof the embodiments.

Reference will now be made in detail to several embodiments, examples ofwhich are illustrated in the accompanying figures. It is noted thatwherever practicable, similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments for purposes of illustration only.

Overview

Many operators in the field posses a personal mobile phone or are issueda mobile phone by their agency or department. Oftentimes a traditionalbug and accompanying support team are unavailable to support an operatorin the field or are not appropriate for a given scenario. However, theagency may still desire to monitor and/or record the operator'sactivities. Accordingly, the agency may coordinate with an agencysupport service for configuring the operator's mobile phone to fulfillthe role of a traditional bug. The configuration can take placeover-the-air such that a given mobile phone is conveniently converted asneeded. In some instances, the mobile phone requires nothing more than aradio connection and dialer. Additionally, if the agency desires tomonitor additional operators, the agency can specify additional mobilephones for operation as bugs.

Example embodiments described herein relate to configuring a wirelessradio network (e.g., Cellular Network and/or WiFi) capable device, suchas a mobile phone, as a one-way recorded transmitter or “mobile bug” foruse in the field. As mobile phones and similar devices are commonlycarried by operators during the course of undercover investigations,mobile phones offer an existing platform for transmitting datawirelessly. Use of such devices as a mobile bug often allows the mobilebug to be concealed “in plain sight” as a direct result of the devices'popularity and utility. Additionally, with the popularity of smartphones and feature phones, additional monitoring and safety features areintegrated into the mobile bug for enhancing operational viability inthe field.

Furthermore, because a mobile phone configured as a mobile bugcommunicates information over existing channels created for the phone'sintended purpose, the mobile bug, if examined, at worst appears tooperate as expected (e.g., receives and/or transmits wireless data).Accordingly, the worst case scenario for an operator is having to“turn-off” the mobile bug rather than having their cover blown.Additionally, by turning a mobile phone into a covert transmittingdevice and using a cellular network as the means of transmission, themobile bug system offers a virtually unlimited range of transmission andthe ability to collect a wide range of valuable real-time data.Real-time data collected by the mobile bug may include audio, video orstill images, Global Positioning System (“GPS”) coordinates, etc.

The mobile bug subsequently transmits all or a portion of the collectedreal-time data wirelessly over the existing channels (e.g., a network)back to the agency, agency service or another entity. Embodiments of theagency, agency service and/or other entities within the mobile bugsystem receive the collected data for storage and/or live streaming tomonitoring devices. Depending on the embodiment, the monitoring devicesare further configured to access and present (e.g., play and/or display)a variety of the real-time and historical data stored on or streamed bythe entities on the network. For example, the monitoring devices mayaccess a web interface, API or execute a standalone application forviewing mobile bug details and the collected information. In someembodiments, the monitoring devices may access portions of the real-timedata via a provided monitoring line configured for maintaining theoperator's cover. Furthermore, other agencies with appropriatecredentials and monitoring devices may similarly access portions of thecollected information during inter-agency investigations.

Environment and Implementation of the Mobile Bug System

Figure (FIG.) 1A is a block diagram illustrating an environment 100 forimplementing a mobile bug 105 system according to one exampleembodiment. As shown the environment 100 includes a network 120connecting agency 100A and 100B, an agency support service provider“agency service” 115 and mobile bugs 105A through 105D. While only oneagency service 115 and two agencies 110 are shown in FIG. 1A forclarity, embodiments can have many agencies 110 and multiple agencyservice providers 115. Additionally, in some embodiments, the agencyservice 115 may be consolidated at an agency 110.

Agency service 115 represents a collection of compute devices (e.g.,servers) and related storage mediums that are used to execute module forperforming various activities such as configuring mobile bugs 105,exchanging data over the network 120 and storing data in support of oneor more agencies 110A, 100B and operated mobile bugs 105. For example,the agency service 115 may include one or more modules providingascribed functionality to an agency 110 via an application programminginterface (“API”) or web interface, collectively “the monitoringinterface”, as described in more detail with reference to FIG. 1B. Theagency service 115 may also include infrastructure for providing audioand video communicability (e.g., internally and/or over the network 120)within the monitoring interface using the public switched telephonenetwork (“PSTN”), voice over internet protocol (“VoIP”) and videoconferencing services.

Agency 110A and 110B represent collections of servers, desktop, notebookor tablet computers, mobile telephones and related storage mediums usedby respective agency personnel for executing applications or modules tocommunicate with and receive data from the agency service 115 (e.g., viathe monitoring interface) and other entities on the network 120. Forexample, agency 110 devices may execute a web browser to access a webinterface or execute a mobile or desktop application for communicatingwith an API provided by the agency service 115. An agency 110A may alsoinclude telephonic and video infrastructure enabling audio and videocommunicability (e.g., internally and/or over the network 120) using thepublic switched telephone network (“PTSN”), voice over internet protocol(“VoIP”) and video conferencing services for monitoring or specifyingconfigurations for mobile bugs 105.

The mobile bugs 105 are oftentimes mobile telephonic devices capable ofcollecting data and transmitting data (e.g., wirelessly) over thenetwork 120. Some examples of a mobile bug 105 include a mobile phone,tablet or notebook computer. Example embodiments of the mobile bug as amobile phone include feature phones, smart phones or standard mobilephones. Accordingly, a given mobile phone or other device operated as amobile bug 105 may not necessarily include or support all of thefunctionality ascribed herein to the mobile bug or mobile bug system dueto inherent differences in device capabilities. In some embodiments,other telephonic devices such as land-line phones oare used.

In one embodiment, the mobile bug 105 executes a bug module forcollecting data, transmitting data and maintaining a persistentconnection with entities on the network 120. An example embodiment of abug module is described in more detail with reference to FIG. 2.

In addition to the mobile bugs 105, a number of monitoring devices (notshown) may connect to entities on the network 120 to obtain or presentdata collected from one or more of the mobile bugs. Depending on theembodiment, a monitoring device is a telephonic device that can beoperated within the agency 110 or externally in the field. As referredto herein, a monitoring device is a mobile or stationary telephonicdevice capable of connectivity (e.g., wireless or wired) to a network120 such as an agency 110 network, the internet, PSTN and/or cellularnetwork. Some examples of a monitoring device include a mobile phone,land-line phone, tablet and notebook or desktop computer.

Example embodiments of the monitoring device as a mobile phone caninclude feature phones, smart phones or standard mobile phones.Accordingly, a given mobile phone or other device operated as amonitoring device does not necessarily include or support all of thefunctionality ascribed herein to the monitoring device or the mobile bugsystem due to inherent differences in device capabilities. In oneexample embodiment, the monitoring device executes a monitoring modulefor interfacing with entities on the network 120 to manage mobile bugs105 and view collected data.

The network 120 represents the communication pathway between agencies110, agencies service 115, the mobile bugs 105, monitoring devices andother entities (not shown). In one embodiment, the network 120 includesstandard communications technologies and/or protocols and can includethe Internet and PSTN. Oftentimes, these communications technologiesand/or protocols carry both PTSN and Internet related data. Thus, thenetwork 120 can include links using technologies such as Ethernet,802.11, worldwide interoperability for microwave access (WiMAX),2G/3G/4G mobile communications protocols, worldwide interoperability forPSTN communications, digital subscriber line (DSL), asynchronoustransfer mode (ATM), InfiniBand, PCI Express Advanced Switching, etc.Similarly, the networking protocols used on the network 120 can includemultiprotocol label switching (MPLS), the transmission controlprotocol/Internet protocol (TCP/IP), the User Datagram Protocol (UDP),the hypertext transport protocol (HTTP), the simple mail transferprotocol (SMTP), the file transfer protocol (FTP), etc. The dataexchanged over the network 120 can be represented using technologiesand/or formats including analog audio (e.g., for last mile PSTNcommunications), digital audio and video (e.g., as a file or streamingwith Real Time Streaming Protocol), the hypertext markup language(HTML), the extensible markup language (XML), JavaScript, VBScript,FLASH, the portable document format (PDF), etc. In addition, all or someof the data exchanged over the network 120 can be encrypted usingconventional encryption technologies such as secure sockets layer (SSL),transport layer security (TLS), virtual private networks (VPNs),Internet Protocol security (IPsec), etc. In another embodiment, theentities on the network 120 can use custom and/or dedicated datacommunications technologies instead of, or in addition to, the onesdescribed above. For example, some government agencies and the militarymay operate networks auxiliary to the internet and PSTN.

As used herein, the term “module” refers to computer programinstructions and/or other logic used to provide the specifiedfunctionality. Thus, a module can be implemented in hardware, firmware,and/or software. In one embodiment, program modules formed of executablecomputer program instructions are stored on a non-transitory storagedevice, loaded into memory, and executed by a computer processor as oneor more processes.

FIG. 1B is a block diagram illustrating an operating environment 101 ofa mobile bug 105 according to one example embodiment. As shown, theoperating environment 101 includes a network 120 with components such asthe internet 123, telephony 125 and provider 127. The network 120 mayalso include GPS satellites (not shown) that relay position data tomobile bugs 105 and other devices.

The telephony network 125 may include servers, switches and otherhardware and software for implementing, among other protocols andtechnologies, worldwide interoperability for PSTN communicationsincluding land-lines and 2G/3G/4G wireless protocols. The telephonynetwork 125 also provides mobile devices with the capability to transmitand receive data over the internet 123. The telephony network 125 ismanaged by one or more communication service providers “CSPs” (notshown) that own telephone numbers for use on the PSTN and the CSPs ownnetwork (e.g., a wireless network that communicates with the PSTN).

The provider 127 may include servers, switches and other hardware andsoftware for communicating over the network 120 with CSPs and otherentities. The provider 127 buys or leases numbers for use on thetelephony network 125 from multiple CSPs. The provider 127, in turn,manages numbers provisioned for use by the agency service 115 and thetelephony traffic associated with the numbers. In one embodiment, theprovider 127 allows the agency service 115 to provision one or more ofthe numbers as virtual numbers over the network 120.

Typically, a number used on the telephony 125 network directs to a givenmobile device, VoIP device or land-line device having an associatednumber identity characterized by automatic number identification “ANI”information, or caller identification. Virtual numbers, while stilloperable with the PSTN and CSP networks, are associated with theprovider 127 who handles telephony traffic for the number. Because avirtual number does not direct to an end user device, the provider 127may establish connections with devices dialing the virtual number,record call information such as call audio and caller history (e.g., ona computer readable medium) and stream/provide call information fordownload (e.g., over the network 120).

The provider 127 may also pass/bridge audio (bidirectional orunidirectional) in real-time between two or more telephonic devicesestablishing connections with the same or different virtual numbers (orconnected with the provider 127 via a virtual number). Additionally, asthe virtual numbers are handled by the provider 127, the agency service115 may modify ANI information and caller identification associated withthe virtual number.

In addition to provisioning virtual numbers for the agency service 115,the provider 127 communicates notifications and data associated with thevirtual numbers to the agency service 115 or other entity such as theagency 110A. For example, the provider 127 may notify the agency service115 of an incoming caller to the virtual number and receive instructionsfrom the agency service 115 to connect the caller to the virtual number.The provider 127 may also receive instructions to stop/start recordingsof calls placed to the virtual number and interface with a transcriptionservice to transcribe call audio. In turn, the provider 127 can transmitthe recordings and transcripts to the agency service 115 or other entityon the network 120.

Additionally, the provider 127 may enable or disable inbound and/oroutbound audio for different parties connected to the virtual number andrecordings thereof responsive to instructions received (e.g., via anAPI) from the agency service 115. The provider 127 can receiveinstructions for managing a virtual number as part of the provisioningprocess, prior to an incoming call or in real-time from the agencyservice 115 when connecting an incoming caller to the virtual number. Insome embodiments, the provider 127 communicates directly with the agency110A to provision virtual numbers, transmit notifications and data orreceive instructions. Additionally, the provider 127 itself may functionas a CSP and vice versa.

The agency service 115 receives requests for provisioning and mappingvirtual number from the agency 110A, mobile bug 105 or other monitoringdevice 107. The requests can include number information for provisioningvirtual numbers such as an area code (e.g., 555), country code (e.g.,+44) and/or associated CSP. In turn, the agency service 115 queries theprovider 127 for available virtual numbers matching the request andreturns the matching virtual numbers to the requesting entity. Theagency service 115 subsequently receives a selection of virtual numbersfrom the requesting entity and claims the virtual numbers from theprovider 127. The agency service 115 may optionally allow the entity tospecify ANI and/or caller identification associated with the virtualnumber to spoof the number's identity on the network 120. The agencyservice 115, in turn, transmits instructions to the provider 127 formodifying the number identity. The agency service 115 may optionallyverify the spoofed number identity.. When a virtual number is no longerneeded by the agency 110A, the agency service 115 obtains any audiorecordings or call logs associated with the virtual number and releasesthe number back to the provider 127.

The requests can also include mapping information for configuringclaimed virtual number function in a mapping table. Depending on thedesired configuration, the mapping information may include thetransmitting number of a mobile bug 105 and/or and monitoring device107, virtual number for association with the device and/or desiredfunction of the virtual number (e.g., monitoring number or receivingnumber). One example mapping request may specify a claimed virtualnumber for use as a virtual receiving number (receiving number) thatmobile bugs 105 connect to in order to transmit collected data (e.g.,audio) over the telephony 125 network. In one embodiment, the requestincludes the transmitting number of the mobile bug 105 and a givenclaimed virtual number for configuration as the receiving number. Inresponse to the request, the agency service 115 associates thetransmitting number of the mobile bug 105 with the receiving number andstores the association in a mapping table.

Another example mapping request may specify a claimed virtual number foruse as a virtual monitoring number (monitoring number) that monitoringdevices 107 connect to in order to monitor a receiving number (e.g.,listen to audio a mobile bug 105 transmits to the receiving number). Inone embodiment, the request includes a given claimed virtual number(e.g., the monitoring number) and the receiving number. In response tothe request, the agency service 115 associates the receiving number withthe monitoring number and stores the association in a mapping table.

In some embodiments, a mapping request may optionally include thetransmitting number of a monitoring device 107 which the agency service115 associates with a receiving number or monitoring number to identifythe monitoring device. As multiple monitoring devices 107A, 107B, 107Cmay monitor a mobile bug 105, the agency service 115 may store multipletransmitting numbers of monitoring devices in association with areceiving number or monitoring number in a mapping table.

In practice, agency service 115 consults the mapping table toautomatically identify a device connecting to a virtual number (e.g.,the receiving number) as either the mobile bug 105 or a monitoringdevice 107 based on the device's transmitting number. Thus, for example,an operator of a mobile bug 105 may simply dial the receiving numbermapped to the transmitting number of his phone to activate the mobilebug.

Personnel with a monitoring device 107 that desire to monitor the mobilebug 105 with a mobile or land-line phone at the agency 110A or in thefield can also dial the receiving number. However, as the agency 115does not identify the transmitting number of the device that of themobile bug 105, personnel devices are appropriately identified asmonitoring devices 107. In some embodiments, the agency service 115identifies connecting monitoring device 107 based on a mapping ofmonitoring devices' 107 transmitting numbers to the receiving number.

Additionally, embodiments of the agency service 115 can use the mappingof monitoring devices 107 to the receiving number for instructing theprovider 127 to automatically dial (e.g., from a specified monitoringnumber) or otherwise notify (e.g., a text message or email) monitoringdevices when the mobile bug 105 connects to the receiving number. Theagency service 115 may also notify monitoring devices 107 through themonitoring interface 145 or via text massage or email.

To prohibit unauthorized access to receiving numbers (and monitoringnumbers), the agency service 115 may allow personnel and operators tospecify key-ins when provisioning and/or mapping virtual numbers. Theagency service 115 stores the key-ins in the mapping table or othersuitable database structure and authenticates callers attemptingconnections to the virtual numbers responsive to correct key-ins. Ininstances where the agency service 115 instructs the provider 127 toautomatically dial a monitoring device 107 from a virtual number, theprovider 127 may initially connect the call without outbound audio (ifthe device answers) and then wait (or prompt) for a key-in. In responseto authentication of the key-in, the provider 127 enables outbound audioto the dialed monitoring device 107. Depending on the embodiment, theagency 110A, agency service 115 or provider 127 may store the mappingtable and/or key-ins for device identification and authentication.

In some embodiments, the agency service 115 provides a bug module 135 tothe mobile bug 105. The bug module 135 interfaces with the native dialerof the mobile bug 105 to maintain a persistent connection with aselected virtual number such as the receiving number. Additionally, thebug module 135 may interface with mobile bug 105 software and/orhardware to utilize features such as an image capture device and GPS tocollect real-time image or video and position data. The bug module 135transmits the collected data over the network 120 back to the agencyservice 115 or other entity. The agency service 115, in turn, may storethe collected data for transmission to one or more monitoring devices107 and the agency 110A. Furthermore, the bug module 135 may beconfigured with a password or otherwise disguised when executed toprevent users other than the operator from accessing the modulealtogether and/or particular features that would give away its truenature. The bug module 135 is described in more detail with reference toFIG. 2.

In some embodiments, the agency service 115 includes a monitoringinterface 145 for providing data received from mobile bugs 105 tovarious monitoring devices 107 and/or appliances 150 over the network120. For example, the monitoring interface 145 may provide monitoringdevices 107 with data corresponding to the status (e.g., transmitting ordisconnected) of one or more mobile bugs 105. If the mobile bug 105 istransmitting real-time data, the monitoring interface 145 can streamdata such as audio from the active transmission, GPS coordinates withheading, speed and coordinates of last-reported locations for placementon a map, collected image or video data, and the internet protocoladdress and/or telephone numbers of other personnel monitoring or havingaccess to the mobile bug. In some embodiments, the monitoring interface145 syncs collected data prior to transmission or includes tags in thetransmitted data for synchronization of playback at the monitoringdevice 107. The monitoring interface 145 can also stream, or provide fordownload, previously recorded monitoring sessions.

In some embodiments, the agency service 115 provides a monitoring module140 to monitoring devices 107 for accessing the monitoring interface145. The monitoring module 140 transmits requests associated withconfiguring a mobile bug 105 and receiving real-time data collected bymonitored bugs. For example, the monitoring module 140 may provide auser interface or status dashboard with options for provisioning virtualnumbers, mapping a transmitting number of a mobile bug 105 or monitoringdevice 107 to a given virtual number and assigning key-ins forconnecting to the virtual number. In one embodiment, the dashboardprovides an option to toggle a recording session on or off with theagency service 115. When the recording session is disabled, themonitoring device 105 still receives real-time data, but the agencyservice 115, appliance 150 and provider 127 do not store copied of thecollected data.

The monitoring module 140 may also display real-time status informationfor the mobile bug 105 including current GPS location, tracked GPSlocation, live audio and image data, mapping table information and otherinformation collected from the mobile bug and streamed by the monitoringinterface 145. Similarly, the monitoring module 140 may be used toaccess and playback historic activity associated with a given virtualnumber or mobile bug 105. For example, the monitoring module 140 maydownload files for playback or steam them. In addition to interfacingwith the agency service 115, the monitoring module 140 may interfacewith an appliance 150 that stores (or backs up) collected data withinthe agency 110A. Additionally, the monitoring module 140 may includefunctionality of the bug module 135 and vice versa.

In one embodiment, the agency 110A includes an appliance 150 for storingdata collected by mobile bugs 105. The appliance 150 may utilize themonitoring interface 145 provided by the agency service 115 for updatingstored data or receive data directly from mobile bugs 105. Additionally,the appliance 150 may receive audio recorded on a virtual number andassociated transcripts from the provider 127 or agency service 115. Oneexample embodiment of the appliance 150 also includes its own monitoringinterface (not shown) that enables monitoring devices 107 to accessreal-time and historic data stored on the appliance for the mobile bug105. Monitoring interfaces provided by the agency service 115 orappliance 150 may also be accessible via a web browser for streaming ordownloading data and include the same or similar options.

Additionally, the appliance 150 and agency service 115 may communicateto intermittently update collected data and records at defined intervalsor in response to notifications to download data. During the intervalsor notification periods, the agency service 115 may process the data andperform any necessary actions as desired by mobile bugs 105 ormonitoring device 107 until the data is transferred to the appliance150. In some embodiments, the agency service 115 maintains a persistentconnection with the appliance 150 to facilitate transfer of real-timedata collected by mobile bugs 105 operated in the field.

In one embodiment, the agency service 115 insures that it, and theprovider 127, do not possess data collected by mobile bugs 105 beyondthe time needed to facilitate transfer. However, in mission criticalsituations, operators and other agency 110A personnel cannot rely onlyon the availability of the appliance 150 for storing and maintainingcollected data. Consequently, if the appliance 150 is unable to takepossession of the collected data or go offline during transfer, theagency service 115 and/or the provider 127 may maintain possession ofthe collected data until the appliance 150 is functioning. Furthermore,the agency service 115 and/or provider 127 may determine whetherchecksums, hashes or sizes of transferred data match the appliance's 150version prior to deleting stored data.

In some embodiments, the agency service 115 maintains an applianceinstead of, or in addition to, the agency 110A. In such cases, theappliance may exist as a dedicated piece of hardware or remote storage.Alternatively, embodiments of the appliance 150 may be implemented in acloud computing and storage stack available on the network 120.

Mobile Bug Functionality

FIG. 2 is a block diagram illustrating a bug module 135 according to oneexample embodiment. As mentioned above, the bug module 135 may bedownloaded from the agency service 115 to the mobile bug 105 andexecuted to collect and transmit data to entities on the network 120. Asshown in FIG. 2, the bug module 135 itself includes multiple modules. Inthe embodiment shown in FIG. 2, the bug module 135 includes a connectionmodule 205, GPS module 210, imaging module 215, protection module 220and provisioning module 225. In some embodiments, the functions aredistributed among the modules in a different manner than describedherein. Other embodiments have additional and/or other modules.

The connection module 205 maintains a persistent connection between themobile bug 105 and a virtual number such as the receiving number mappedto the transmitting number of the mobile bug 105. For example, theoperator may move into an area without network 120 service andunknowingly disconnect the mobile bug 105 from the receiving number orotherwise prevent successful transfer of data to an entity on thenetwork. The connection module 205 receives input from the operatorincluding the receiving number associated with the mobile bug 105. Oncea connection with the receiving number is established, the connectionmodule 205 detects network 120 disruptions such as dropped calls,timeouts or packet loss and automatically reestablishes connection withthe receiving number or retries transmission of collected data over thenetwork.

In one embodiment, the connection module 205 communicates with a nativedialer of the mobile bug 106 to redial the receiving number andreestablish the connection without intervention from the operator. Whenthe operator desires to terminate transmission, the connection module205 may receive input from a designated disconnect button to terminatethe call and stop the auto-redialing process.

Depending on the mobile bug's 105 capabilities, the communication module205 may enable placement/receipt of outgoing and incoming calls (e.g.,other than those placed within the module to the receiving number)during monitoring (e.g., via call waiting features) within the nativedialer application or similar. Embodiments of the communication module205 and/or protection module 220 may suppress visual notifications orqueues that the communication module 205 is maintaining a connectionwith the receiving number. In some instances, the communication module205 can pass audio from the inbound or outbound call to the call-waitingconnection with the receiving number to prevent gaps in audiomonitoring.

The GPS module 210 communicates with a native GPS receiver on the mobilebug 105 to receive GPS location data. The GPS module 210 may alsocommunicate with other radio receivers and directional mechanisms (e.g.,compass or accelerometers) on the mobile bug 105 to receive additionallocation data. The GPS module 210 processes the GPS and radio locationdata to determine and refine an estimated location measurement for themobile bug 105. The location measurement may include, but is not limitedto, a latitude, longitude, altitude, heading, speed, associated accuracymeasurement and the time and date of recording. The GPS module 210transmits the determined location measurement over the network 120 theagency service 115 or other entity. In one embodiment, the GPS module210 streams the location measurement in real-time.

The imaging module 215 communicates with a native image sensor on themobile bug 105 for capturing still images or videos. The imaging module215 may downsample (e.g., compress) collected image data fortransmission over the network 120 based on available bandwidth. Thus,for example, the imaging module 215 may stream the collected image datain real-time. High-resolution image data may be stored directly on thedevice for subsequent transmission as bandwidth becomes available.

In some embodiments, a protection module 220 interfaces with theoperating system of the mobile bug 105 to provide options orfunctionality for concealing operations of the bug module 135 on themobile bug 105. For example, the protection module 220 providesoperators with option to run the bug module 135 in the background andonly reveal or access the bug module in response to a specified key-in(e.g., button-press combination, password or other personalidentification). In another example, the protection module 220 mimicsthe look and feel of the native operating system or calling applicationon the phone to conceal use of bug module 135 functionality. However,unlike the native operating system or calling application, theprotection module 220 provides password protection, locking (e.g., witha key-in) or otherwise visually concealed or protected configurationoptions and viewing of current call activity for connections establishedusing the communications module 205.

The provisioning module 225 interfaces with the provider 127 or agencyservices 115 to provision virtual numbers and modify virtual numberassignments and function in the field. Alternatively, a web browser onthe mobile bug 105 may be used.

In some embodiments, the bug module 135 and the modules thereininterface and communicate with non-native devices attached to the mobilebug 105. For example, audio, images and locations data can be determinedfrom accessories coupled (e.g., wired microphone or imaging device) orwirelessly connected (e.g., Bluetooth headset) to the mobile bug 105.

Virtual Number Provisioning

FIG. 3A is an interaction diagram illustrating a method for provisioning300 and mapping virtual numbers for operating and monitoring a mobilebug 105 according to one example embodiment. Initially, the agencyservice 115 receives 310 a request including a calling code forprovisioning 300 a virtual number from a monitoring device 107, mobilebug 105, provided web interface or other entity. The calling code caninclude an area code and country code where the provisioned virtualnumber will be operated.

The agency service 115 queries 320 the provider for virtual numbersmatching the specified calling code. The provider 127 returns 330 a listof available virtual numbers to the agency service 115 which, in turn,transmits the virtual numbers for display to the requestor. The agencyservice 115 receives 335 one or more virtual number selections andclaims 340 each selected virtual number from the provider 127. Theagency service 115 may optionally include corresponding ANI and calleridentification information for a virtual number that may be edited onthe requesting device 105, 107 or in the web interface. The agencyservice 115 subsequently stores the modified virtual number informationand instructs the provider 127 to update the associated virtual numberinformation.

With one or more virtual numbers claimed, the agency service 115 canreceive mapping requests for the virtual numbers and, in turn, map 350the virtual numbers responsive to information in the mapping request.For example, the requestor may be prompted to enter the transmittingnumber of a mobile bug 105 for association with a virtual number to beused as a receiving number. The agency service 115 stores thetransmitting number of the mobile bug 105 and the receiving number in amapping table (e.g., at the agency service 115 or on the appliance 150).The requestor may modify the mapping at any time, without anyinterruption of service at the receiving number.

Oftentimes, receiving numbers have a different country code (or areacode) than monitoring devices 107 connecting to the receiving number tomonitor the mobile bug 105. In some cases, the requestor knows thecountry code or area code where the monitoring devices 107 are located.Accordingly, to avoid costly charges for the agency 110A, the agencyservice 115 allows the requestor to provision additional virtual numberswith the known country codes and area codes for use as monitoringnumbers. The agency service 115 may then receive mapping requests forthe monitoring numbers and, in turn map monitoring numbers to specifiedreceiving numbers.

When a monitoring device 107 subsequently dials a monitoring number, theagency service 115 identifies the associated receiving number from themapping table and instructs the provider 127 to connect the monitoringdevice 107 to the receiving number or pass audio from the receivingnumber to the monitoring number and connect the monitoring device to themonitoring number.

In some embodiments, monitoring numbers can be tied to the transmittingnumber of a mobile bug 105 for automatic mapping to receiving numbers.For example, an operator using the same mobile bug 105 for multipleinvestigations may utilize a different receiving number for eachinvestigation (e.g., to keep distinct records). Rather than requiringthe operator or personnel monitoring the operator to assign monitoringnumbers (or frequently modify mapping) to each receiving number on anindividual basis, a monitoring number can be tied to the mobile bug 105.When the mobile bug 105 is mapped or used with a receiving number, theagency service 115 maps the tied monitoring number to the receivingnumber. In such a way, a given monitoring number may be dedicated tomonitoring a particular mobile bug 105. A requestor may re-specify themapping configuration as needed to change or swap claimed virtualnumbers and transmitting numbers between receiving numbers andmonitoring numbers.

Example embodiments of monitoring device 107 mapping to receivingnumbers and/or monitoring numbers can be performed in the same orsimilar fashion as mobile bug 105 mappings.

FIG. 3B is a table illustrating an example embodiment of virtual numbermapping 350 for operating and monitoring a mobile bug 105. As shown,mapping table 360A includes a number of receiving numbers 363A mapped tocorresponding transmitting numbers 361A (e.g., of mobile bugs 105).

When the agency service 115 receives connection requests to receivingnumbers 363A from the network 120, the agency service identifies theconnecting device as the mobile bug 105 based on the transmitting number361A stored in the mapping table 360A. If the connecting device's numberdoes not match the transmitting number 361A, the agency service 115identifies the device as a monitoring device 107.

Prior to connecting the monitoring device 107 to the receiving number,the agency service 115 may wait or instruct the provider 127 to wait forkey-in of a specified password. If an improper password or no passwordis received, the monitoring device 107 is disconnected. In oneembodiment, the monitoring device 107 must enter the password within agiven time period (e.g., 10-30 seconds) without being prompted tomitigate suspicion if the line is dialed by another party. In someembodiments, the mapping table 360A further includes mappings ofmonitoring device 107 transmitting numbers to explicitly identifymonitoring devices in addition to mobile bugs 105.

FIG. 3C is a table illustrating an example embodiment of virtual numbermapping 350 for operating and monitoring a mobile bug 105. As shown,mapping table 360B includes a number of receiving numbers 363B mapped tocorresponding transmitting numbers 361B (e.g., of mobile bugs 105).Additionally shown are a number of monitoring numbers 365 mapped to thereceiving numbers 363B.

When the agency service 115 receives connection requests to monitoringnumbers 365 from the network 120, the agency service automaticallyidentifies the connecting device as a monitoring device 107 andidentifies the associated receiving number 363B from the mapping table360B. The agency service 115, in turn, instructs the provider 127 toconnect the monitoring device 107 with the receiving number 363B (e.g.,directly, or through the monitoring number 365). Prior to connecting themonitoring device 107, key-in of a specified password may be required.In some embodiments, the mapping table 360A further includes mappings ofmonitoring device 107 transmitting numbers to explicitly identifymonitoring devices in addition to mobile bugs 105.

FIG. 4 is an interaction diagram illustrating a method for connecting400 a monitoring device 107 or mobile bug 105 to a virtual numberaccording to one example embodiment. Once the agency service 115provisions 300 a virtual number with the provider 127, a mobile bug 105or monitoring device 107 may connect 400 to the virtual number. Toactivate a mobile bug 105 the operator may simply dial 410 the receivingnumber mapped to his mobile phone. Similarly, personnel using amonitoring device 107 may dial 410 the receiving number mapped to themobile bug 105 to monitor the bug. Alternatively, personnel using amonitoring device 107 may dial 410 the monitoring number mapped to thereceiving number.

The provider 127 receives the connection request via the telephonynetwork 125 and identifies 420 the dialed number as a virtual numberprovisioned 300 by agency service 115. Accordingly, in embodiments wherethe agency service 115 stores the mapping table, the provider 127 passesthe transmitting number of the device attempting to connect to thevirtual number to the agency service 115.

The agency service 115, in turn, identifies 430 the device attempting toconnect to the virtual number as either the mobile bug 105 or amonitoring device 107 from the mapping table. In the case of the mobilebug 105, the agency service 115 determines that the transmitting numberstored in the mapping table for the dialed receiving number matches thenumber of device attempting to connect to the receiving number. Theagency service 115 then instructs the provider 127 to connect 440 thedevice to the receiving number as the mobile bug 105 and disable (e.g.,mute) outgoing audio to the mobile bug.

In one embodiment, the agency service 115 identifies 430 devices withnumbers that do not match the transmitting number stored in the mappingtable for a receiving number as monitoring devices 107. The agencyservice 115 then instructs the provider 127 to connect 440 the device tothe receiving number as a monitoring device 107.

If the agency service 115 determines that the device is attempting toconnect to a monitoring number, the agency service 115 identifies 430the device as a monitoring device 107. The agency service 115 thendetermines which receiving number the monitoring number is mapped to andinstructs the provider 127 to connect 440 the device to the receivingnumber (e.g., directly or via the monitoring number) as a monitoringdevice 107.

The monitoring devices 107 may communicate with other devices monitoringthe mobile bug 105 (e.g., like a conference call between the receivingnumber and/or monitoring numbers) although no audio is transmitted tothe mobile bug. Additionally, the provider 127 or agency service 115 mayprovide the monitoring devices 107A with key combinations (e.g., *1, 2,etc.) to mute other monitoring devices 107, the mobile bug 105 or theirown device.

In some embodiments, the PSTN or provider 127 fails to pass thetransmitting number associated with a mobile bug 105 (or monitoringdevice 107) to the provider or agency service 115. For example, theprovider 127 or agency service 115 may receive a number other than themobile bug's 105 and incorrectly identify the mobile bug. Some examplePSTN and provider 127 failures are all zeroes numbers (+00000-000-0000), restricted numbers (737-874-2833) or simply an incorrectnumber for the mobile bug 105. In any instance, the agency service 115may be unable to identify the mobile bug 105 by the receivedtransmitting number.

The agency service 115 can recognize that some numbers are passedincorrectly (e.g., a restricted number or zeroes number). In response,the agency service 115 may play a prompt or instruct the provider 127 toplay a prompt such as “press 1 for a mobile bug or press 2 for amonitoring device.” In practice, the prompt can be ambiguous (e.g.,please enter the extension of the party you are trying to reach orsimilar) for the safety of the operator if another party dials thevirtual number. Operators or personnel may then key-in as using a mobilebug 105 or monitoring device 107.

Alternatively, as the key-ins of the mobile bug 105 and monitoringdevice 107 typically differ, the agency service 115 may instruct theprovider 127 to simply play a generic tone or number not availablerecording to notify users that they need to key-in. The matching of akey-in with stored authentication information identifies and activatesthe connecting device as the mobile bug 105 (or monitoring device 107).

In some embodiments, the agency service 115 may prompt all connectingdevice to key-in for identification. For example, an agency 110A maywant to enable the option to use unmapped devices as mobile bugs 105 ona specified receiving number.

Operating a Mobile Bug

FIG. 5 is an interaction diagram illustrating a method for operating 500a mobile bug 105 according to one example embodiment. Once theconnection 400 between the mobile bug 105 and the receiving number isestablished, the provider 127 records audio on the line from the mobilebug.

The mobile bug 105 collects 510 audio data using a microphone coupled tothe mobile bug. The mobile bug 105, in turn, transmits 520 the collectedaudio data to the provider 127 by way of the connection to the receivingnumber. The provider 127, in addition to enabling monitoring devices 107to connect to the receiving number, transmits the audio data receivedfrom the mobile bug 105 to the agency service 115 or appliance 150 overthe network 120.

The mobile bug 105 may also collect 510 image data using an image sensorcoupled to the mobile bug. The mobile bug 105, in turn, transmits 520the collected image data to the agency service 115. In some embodiments,the mobile bug 105 downsamples collected image data (e.g., based onavailable network 120 bandwidth) such that mobile bug 105 can streamimage or video in real-time.

Furthermore, the mobile bug 105 may also collect 510 location data fromGPS receivers and other direction mechanism coupled to the mobile bug.The mobile bug 105 determines a location measurement including theposition of the mobile bug, direction and speed of the mobile bug andassociated accuracy of the measurement. The mobile bug 105 transmits 520the location measurement to the agency service 115. In some embodiments,the mobile bug 105 determines and transmits 520 the locationmeasurements in real-time to the agency service 115.

In some instances, the connection 400 between the mobile bug 105 and thereceiving number (e.g., via the provider 127) or the agency service 115may be terminated or timeout. In the case of a disconnection from thereceiving number, the mobile bug 105 attempts to reestablish 540 theterminated connection in the background by redialing the receivingnumber and automatically providing any necessary key-in information. Toreestablish 540 a connection with the agency service 115, the mobile bug105 may intermittently test network 120 availability and subsequentlyconnect to the agency service 115 when able.

In one embodiment, the mobile bug transmits 520 data collected duringdisconnect periods in the background of real-time data. For example,while the provider 127 typically handles audio data via the receivingnumber, the agency service 115 may receive any audio data collectedduring disconnect periods. Accordingly, the agency service 115 mayupdate 530 the appliance 150 with the received audio data. The agencyservice 115 or provider 127 can also update 530 the appliance with anyother data received from the provider 127 and/or mobile bug 105.

Monitoring a Mobile Bug

FIG. 6 is an interaction diagram illustrating a method for monitoring600 a mobile bug 105 according to one example embodiment. As describedabove, the agency service 115 receives 610A collected data from themobile bug and/or the provider 127. Additionally, the provider 127 mayreceive data 610B from the mobile bug 105. In turn, the agency service115 and/or provider 127 may update 530 the appliance at the agency 110.A monitoring device 107 may subsequently monitor 600A, 600B the mobilebug 105 using one or both of the processes outlined below.

In one embodiment, the monitoring device 107 connects 400 to a receivingnumber or monitoring number for monitoring 600A the mobile bug 105. Themonitoring device 107 may be connected 400 by answering an incoming callfrom the monitoring or receiving number initiated by the provider 127 ordialing a virtual number directly as described with reference to FIG. 4.

Once the connection between the monitoring device 107 and the receivingnumber or monitoring number is established, the monitoring device 640receives the live audio transmitted to the receiving number from themobile bug 105. To continue monitoring 600A the mobile bug 107, themonitoring device 107 simply maintains the connection 400 with thereceiving number or monitoring number.

In another embodiment, the monitoring device 107 connects 650 to theagency service 115 and/or appliance 150 for monitoring 600B the mobilebug 105. The monitoring device 107 may establish the connection 650using a web browser or monitoring module 140 that retrieves or streamscollected data via a monitoring interface on the appliance 150 or agencyservice 115 (e.g., monitoring interface 145).

In one example embodiment, the monitoring device 107 streams 660 image,audio and/or location measurements in real-time from the agency service115. In addition, the monitoring device 107 can retrieve 670 historicaldata stored on the appliance 150 to view previous mobile bug 105operating sessions 500. In some embodiments, the appliance 150 alsosupports real-time monitoring.

In some instances, the monitoring device 107 receives notifications fromthe monitoring interface 145 for display in the web browser or with themonitoring module 140. Example notifications include audio or visualalerts for notifying personnel if the mobile bug 105 stops transmittingreal-time data to the receiving number, appliance 150 or agency service115. If the mobile bug 105 reestablishes a connection, the monitoringdevice 107 may also receive notifications when real-time data streaminghas resumed or when data collected by the mobile bug 105 during thedisconnected period becomes available

SUMMARY

The foregoing description of the embodiments has been presented for thepurpose of illustration; it is not intended to be exhaustive or to limitthe disclosure to the precise forms disclosed. Persons skilled in therelevant art can appreciate that many modifications and variations arepossible in light of the above disclosure.

Some portions of this description describe the embodiments in terms ofalgorithms and symbolic representations of operations on information.These algorithmic descriptions and representations are commonly used bythose skilled in the data processing arts to convey the substance oftheir work effectively to others skilled in the art. These operations,while described functionally, computationally, or logically, areunderstood to be implemented by computer programs or equivalentelectrical circuits, microcode, or the like. Furthermore, it has alsoproven convenient at times, to refer to these arrangements of operationsas modules, without loss of generality. The described operations andtheir associated modules may be embodied in software, firmware,hardware, or any combinations thereof

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices.

Embodiments may also relate to an apparatus for performing theoperations herein. This apparatus may be specially constructed for therequired purposes, and/or it may comprise a general-purpose computingdevice selectively activated or reconfigured by a computer programstored in the computer. Such a computer program may be stored in anon-transitory, tangible computer readable storage medium, or any typeof media suitable for storing electronic instructions, which may becoupled to a computer system bus. Furthermore, any computing systemsreferred to in the specification may include a single processor or maybe architectures employing multiple processor designs for increasedcomputing capability.

Embodiments may also relate to a product that is produced by a computingprocess described herein. Such a product may comprise informationresulting from a computing process, where the information is stored on anon-transitory, tangible computer readable storage medium and mayinclude any embodiment of a computer program product or other datacombination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the disclosure be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsis intended to be illustrative, but not limiting, of the scope of thedisclosure, which is set forth in the following claims.

1. A computer based method for configuring a telephonic device as aone-way recorded transmitter (mobile bug), the method comprising:receiving information in response to a connection request from thetelephonic device to a virtual number, the information including atransmitting number corresponding to the telephonic device and thevirtual number; identifying the telephonic device as the mobile bug inresponse to matching the transmitting number of the telephonic devicewith a transmitting number stored in association with the virtual numberin a mapping table; and transmitting instructions for connecting themobile bug to the virtual number to permit monitoring of the mobile bug,wherein outgoing audio to the mobile bug is disabled.
 2. The method ofclaim 1, further comprising: receiving information in response to asecond connection request from a second telephonic device to a secondvirtual number, the information including a transmitting numbercorresponding to the second telephonic device and the second virtualnumber; identifying the second telephonic device as a monitoring deviceof the mobile bug; and transmitting instructions for permitting themonitoring device to monitor the mobile bug.
 3. The method of claim 2,wherein the second virtual number is the same as the first virtualnumber and the second telephonic device is identified as the monitoringdevice of the mobile bug in response to a lack of match between thetransmitting number of the second telephonic device with thetransmitting number stored in association with the first virtual numberin the mapping table.
 4. The method of claim 2, wherein the secondvirtual number is different from the first virtual number and the secondtelephonic device is identified as the monitoring device of the firstvirtual number in response to matching the second virtual number with avirtual monitoring number stored in association with the first virtualnumber in the mapping table.
 5. The method of claim 2, wherein theinstructions permitting the monitoring device to monitor the mobileinclude instructions for connecting the monitoring device with thesecond virtual number and passing audio collected at the mobile bug tothe monitoring device.
 6. The method of claim 1, further comprisingtransmitting instructions for recording audio transmitted by the mobilebug.
 7. The method of claim 2, wherein the mapping information for thesecond virtual number includes a key-in for authenticating connectionrequests to monitor the mobile bug.
 8. The method of claim 7, furthercomprising transmitting instructions for connecting the monitoringdevice to the second virtual number in response to authentication ofkey-in information corresponding to the second connection request. 9.The method of claim 1, further comprising providing a bug module to themobile bug for: interfacing with features of the mobile bug to collectreal-time information; and maintaining a persistent connection fortransmitting the real-time information.
 10. The method of claim 9,wherein the real-time information includes at least one of an estimatelocation measurement, still image data and video data, wherein theestimate location measurement of the mobile bug is based on globalpositioning coordinates.
 11. The method of claim 2, further comprising:receiving real-time information corresponding to the mobile bug; andstreaming the real-time information to the monitoring device.
 12. Themethod of claim 1, further comprising: provisioning the virtual numberbased on number information received for the virtual number; receivingmapping information for the virtual number, the mapping informationincluding a transmitting number corresponding to the mobile bug; andstoring the virtual number in the mapping table as a receiving number inassociation with the transmitting number corresponding to the mobilebug.
 13. The method of claim 1, wherein the first telephonic device is amobile phone.
 14. A system for configuring a telephonic device as aone-way recorded transmitter (mobile bug), the system comprising: aserver comprising one or more processors and a non-transitorycomputer-readable storage medium storing computer program code, thecomputer program code when executed performing steps comprising:receiving information in response to a connection request from thetelephonic device to a virtual number, the information including atransmitting number corresponding to the telephonic device and thevirtual number; identifying the telephonic device as the mobile bug inresponse to matching the transmitting number of the telephonic devicewith a transmitting number stored in association with the virtual numberin a mapping table; and transmitting instructions for connecting themobile bug to the virtual number to permit monitoring of the mobile bug,wherein outgoing audio to the mobile bug is disabled.
 15. The system ofclaim 14, wherein the server further comprises program code for:receiving information in response to a second connection request from asecond telephonic device to a second virtual number, the informationincluding a transmitting number corresponding to the second telephonicdevice and the second virtual number; identifying the second telephonicdevice as a monitoring device of the mobile bug; and transmittinginstructions for permitting the monitoring device to monitor the mobilebug.
 16. The system of claim 14, wherein the server further comprisesprogram code for: provisioning the virtual number based on numberinformation received for the virtual number; receiving mappinginformation for the virtual number, the mapping information including atransmitting number corresponding to the mobile bug; and storing thevirtual number in the mapping table as a receiving number in associationwith the transmitting number corresponding to the mobile bug.
 17. Thesystem of claim 16, wherein the mapping information received for thevirtual number includes a key-in for authenticating monitoring devicesrequesting to monitor the mobile bug, the server further comprisingprogram code for authenticating a second telephonic device requesting tomonitor the mobile bug responsive to key-in information received for thesecond telephonic device.
 18. The system of claim 14, furthercomprising: a second server comprising one or more processors and acomputer-readable storage medium storing computer program code, thecomputer program code when executed performing steps comprising:identifying connection requests from telephonic devices to the virtualnumber; receiving instructions for connecting the telephonic device tothe virtual number as a mobile bug with outgoing audio disabled;establishing a connection to the telephonic device; and disablingoutgoing audio to the telephonic device.
 19. The system of claim 18, thesecond server further comprises program code for: receiving instructionsfor connecting a second telephonic device to the virtual number as amonitoring device; establishing a connection to the second telephonicdevice; and passing audio received from the first telephonic device tothe second telephonic device.
 20. The system of claim 18, the secondserver further comprises program code for recording audio received fromthe mobile bug.